Skip to content

Fill gaps from assistant conversations: risk levels and Support tickets - #467

Closed
mintlify[bot] wants to merge 1 commit into
mainfrom
mintlify/ce853e25
Closed

Fill gaps from assistant conversations: risk levels and Support tickets#467
mintlify[bot] wants to merge 1 commit into
mainfrom
mintlify/ce853e25

Conversation

@mintlify

@mintlify mintlify Bot commented Aug 21, 2026

Copy link
Copy Markdown
Contributor

Summary

Address two recurring assistant conversation gaps: whether entitlements have a default risk level, and how to submit a C1 Support ticket.

Changes

  • product/admin/global-settings.mdx: Note that C1 does not apply a default risk level automatically—entitlement risk level is unset until assigned individually or in bulk.
  • developer/community.mdx: Add a "Submit a C1 Support ticket" subsection with the support email and the information to include.

Context

Assistant conversation buckets over the past week showed:

  • An unanswered thread asking whether a default risk level can be applied to every entitlement.
  • A "how do I submit a support ticket" thread where the assistant confirmed the docs list the Support channel but don't say how to open a ticket.

Baton-http account provisioning and other buckets were verified against the repo and are already covered accurately.

@mintlify

mintlify Bot commented Aug 21, 2026

Copy link
Copy Markdown
Contributor Author

Preview deployment for your docs. Learn more about Mintlify Previews.

Project Status Preview Updated (UTC)
conductorone 🟢 Ready View Preview Aug 21, 2026, 6:17 PM

@mindymo

mindymo commented Sep 1, 2026

Copy link
Copy Markdown
Collaborator

Support ticket via email isn't correct, will add attribute note by hand.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant